Managing visual voicemail from multiple devices

ABSTRACT

A network device may include a memory to store a database including voicemail message information associated with a voicemail mailbox, a transmitter, and a receiver. The transmitter may send a notification to each of a plurality of communication devices, the notification including an indication of a number of new voicemail messages in the voicemail mailbox, an indication of a total number of voicemail messages in the voicemail mailbox, and an identifier of a most recent voicemail message in the voicemail mailbox, where each of the plurality of communication devices uses the notification signal to determine whether to request a list of voicemail messages. The receiver may receive, from one of the communication devices in response to the notification, a request for the list of voicemail messages associated with voicemail message information stored in the database. The transmitter may sends, to the one of the plurality of communications devices, the list of voicemail messages.

RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.12/236,808 filed Sep. 24, 2008, which claims the benefit of (1) U.S.Patent Application No. 61/013,549 filed Dec. 13, 2007, and (2)provisional U.S. Patent Application No. 61/018,044, filed Dec. 31, 2007,the disclosures of these two applications being incorporated herein byreference.

BACKGROUND INFORMATION

Visual voicemail is a user friendly application that adds a visualaspect to managing voicemail messages. Visual voicemail may enablemobile phone users to manage voicemail message in an order of theirchoice, e.g., in a random order rather than a sequential order.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1A is a block diagram of an exemplary environment in whichembodiments disclosed herein may be implemented;

FIGS. 1B, 1C, and 1D show exemplary visual voicemail graphical userinterfaces;

FIG. 2 is a block diagram of an exemplary network in which embodimentsdescribed herein may be implemented;

FIG. 3 is a block diagram of an exemplary user device;

FIG. 4 is a block diagram of exemplary components of a client computermodule;

FIG. 5 is a block diagram of exemplary components of a server computingmodule;

FIGS. 6A and 6B are diagrams of exemplary message tables;

FIGS. 7A and 7B are block diagrams of exemplary aggregate messagetables;

FIG. 8 is a block diagram of an exemplary notification table;

FIGS. 9A and 9B are flowcharts of exemplary processes for receiving avoicemail and notifying a user device of voicemail information;

FIG. 10 is a diagram of exemplary network signals for notifying a userdevice of voicemail information;

FIG. 11 is a flowchart of a process for synchronizing voicemail messageinformation;

FIG. 12 is a diagram of exemplary network signals for synchronizingvoicemail message information;

FIG. 13 is a flowchart of an exemplary process for listening to avoicemail message;

FIG. 14 is a diagram of exemplary network signals for listening to avoicemail message; and

FIG. 15 is a flowchart of an exemplary process for changing the state ofa voicemail message.

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

The following detailed description refers to the accompanying drawings.The same reference numbers in different drawings may identify the sameor similar elements. Also, the following detailed description does notlimit the invention.

A person may have multiple communication devices, such as a home phone,a mobile phone, a smart phone, a personal digital assistant (PDA), acomputer, etc. Each of these devices may be associated with a mailboxfor receiving voicemail messages. One or more embodiments disclosedherein may allow for the management of any one of these mailboxes fromeach of the communication devices. For example, FIG. 1A is a blockdiagram of an exemplary environment 100 in which embodiments disclosedherein may be implemented. Environment 100 includes a work phone 101, ahome phone 102, a mobile phone 103, and a work voicemail (VM) server104. In this example, work VM server 104 may store voicemail messages ina mailbox for unanswered calls to work phone 101. In embodimentsdisclosed herein, a user may manage the voicemail mailbox in the work VMserver from the user's work phone 101, as usual, but may also manage themailbox from home phone 102 and mobile phone 103. In one embodiment,actions taken by the user on voicemail messages using one device (e.g.,mobile phone 103) may be reflected on all of the user's devices (e.g.,work phone 101, home phone 102, and mobile phone 103). For example, ifthe user deletes a voicemail message in work VM server 104 using mobilephone 103, this change may be reflected in work phone 101 and home phone102, as well as mobile phone 103.

FIGS. 1B, 1C, and 1D show exemplary visual voicemail (VVM) graphicaluser interfaces (GUIs) for a communication device, such a portablecommunication device (e.g., a mobile phone). FIG. 1B shows an exemplarypop-up screen for notifying a user that there are three new voicemailmessages waiting in the user's voicemail box. FIG. 1B also shows thatthe user may select to ignore the voicemail messages (e.g., using abutton 105) or listen to the voicemail messages (e.g., using a button106). If the user selects to listen to the voicemail messages, the usermay be presented with the GUI shown in FIG. 1C, for example.

FIG. 1C shows an exemplary list of voicemail messages including, foreach voicemail, the name of the caller, the phone number of the caller,the time of the call, and the length of the voicemail message. Inaddition, the GUI of FIG. 1C may present an icon for each voicemailmessage indicating the mailbox in which the voicemail was left ordeposited. For example, a building icon 108 may indicate that a messagewas left in the user's work mailbox; a house icon 110 may indicate thata message was left in the user's home mailbox; and a mobile-phone icon112 may indicate that a message was left in the user's mobile-phonemailbox.

The exemplary GUIs of the communication device may allow a user tomanage the selected voicemail message. In the exemplary GUI of FIG. 1C,the user may scroll to and select any of the listed voicemail messagesin any order. For example, a voicemail message 120 (in the user'smobile-phone mailbox) from Bob Sherman is highlighted for selection. Theuser may delete the selected voicemail message (e.g., using a button114) or play the selected voicemail message (e.g., using a button 116).If the user selects to play the voicemail, the user may be presentedwith the GUI shown in FIG. 1D, for example.

FIG. 1D shows an exemplary voicemail message being played. As shown inFIG. 1D, the user may delete the selected message (e.g., using a button122 or a key labeled “7” on a numeric keypad); may save the message(e.g., using a button 124 or a key labeled “9” on the numeric keypad);may initiate a call to the party that left the voicemail message (e.g.,using a button 126 or a key labeled “5” on the numeric keypad); mayrewind the message (e.g., using a button 128); may fast-forward themessage (e.g., using a button 130); or may pause the message (e.g.,using a button 132). In one embodiment, management actions taken on amessage using one communication device may be reflected on one or moreother communication devices that may manage the same mailbox.

FIG. 2 shows an exemplary network 200 in which embodiments describedherein may be implemented. As shown, network 200 may include a devicelayer 202, a voice-mail (VM) layer 204, and a VVM layer 206. VVM layer206 may lie between device layer 202 and VM layer 204 and may facilitatethe exchange of messages (e.g., communications) between device layer 202and VM layer 204.

Device layer 202 may include, for example, a computer 208, a television(TV) 210, a smart phone 216 (e.g., a Blackberry, Treo, etc.), a PDA 218,a mobile phone 220, and/or another type of communication device. Any ofdevices 208-220 may be considered user devices. VM layer 204 may includeVM servers 232-236 (e.g., a work VM server 232, a home VM server 234,and a wireless VM server 236), and a service-wide directory (SWD) server238. VVM layer 206 may include a VVM server 252, a device proxy 254, anSMPP (Short Message Peer-to-Peer Protocol) gateway server 256, anauthentication server 258, a notification server 260, and a VVM gatewayserver 262.

Computer 208 may include one or more computer systems for hostingprograms, databases, and/or applications. Computer 208 may include alaptop, desktop, or any other type of computing device. Computer 208 mayinclude a browser application program for navigating a network, such asthe Internet.

TV 210 may include a device capable of receiving and reproducing videoand audio signals, e.g., a video display device. TV 210 may include aliquid crystal display (LCD), a cathode ray tube (CRT), a plasmadisplay, etc.

TV 210 may be associated with a set-top box (STB) (not shown). The STBmay include a computer device, such as a cable card, for hostingprograms, databases, and/or applications. In one embodiment, TV 210 mayinclude the STB in the same housing. TV 210 and/or the STB may include avisual voicemail application to receive, listen to, and/or sendvoicemail messages. TV 210 and/or the STB may be associated with aremote control (not shown). The remote control may include control keysto navigate menus displayed on TV 210, for example, and to otherwisecontrol functions of TV 210 and/or the STB. The remote control maytransmit infrared signals, or another type of signals, to an inputdevice associated with the STB and/or TV 210.

Smart phone 216, PDA 218, and/or mobile phone 220 may allow a user toplace telephone calls to other user devices. Smart phone 216, PDA 218,and/or mobile phone 220 may communicate with other devices via one ormore communication towers (not shown) using a wireless communicationprotocol, e.g., GSM (Global System for Mobile Communications), CDMA(Code-Division Multiple Access), WCDMA (Wideband CDMA), GPRS (GeneralPacket Radio Service), EDGE (Enhanced Data Rates for GSM Evolution),etc. In one embodiment, smart phone 216, mobile phone 220, and/or PDA218 may communicate with other devices through a wireless local networkusing WiFi (e.g., IEEE 802.11x).

In other embodiments, smart phone 216, PDA 218, and/or mobile phone 220may also communicate with other devices via a wired network. Forexample, smart phone 216, mobile phone 220, and PDA 218 may communicatewith other devices using a public-switched telephone network (PSTN) orthe Ethernet protocol. Smart phone 216, PDA 218, and mobile phone 220may include a visual voicemail application to receive, listen to, and/orsend voicemail messages.

Work VM server 232, home VM server 234, and wireless VM server 236 mayeach receive and store voicemail messages in mailboxes associated withone or more user devices, such as user devices 208-220. Examples of VMservers include the Lucent Automatic Call Distributor (ACD) server andthe Comverse Voicemail Service Node (VSN) server. VM servers 232-236 mayreceive voicemail messages when, for example, a user does not answer acall request. VM servers 232-236 may deliver the voicemail messages whenrequested, for example, to one of user devices 208-220 or VVM server252. In one embodiment, VM servers 232-236 may store video voicemail, aswell as audio voicemail. In one embodiment, VVM server may aggregatevoicemail information from work VM server 232, home VM server 234,and/or wireless VM server 236.

In one exemplary embodiment, user devices 208-220 may be associated witha single user. For example, a user may have been issued smart phone 216and computer 208 (which may include a soft phone) by an employer to beused for work. The same user may own mobile phone 220 for personal useand may have TV 210 at home for family use. The same user may also ownPDA 218 that may be used as a personal address book as well as a homephone. In this exemplary embodiment, work VM server 232 may receive andstore voicemail for smart phone 216; home VM server 234 may receive andstore voicemail for PDA 218; and wireless VM server 236 may receive andstore voicemail for mobile phone 220. Although user devices 208-220 maybe associated with one user in this example, VM servers 232-236 maystore voicemails for more than one user (e.g., thousands or hundreds ofthousands of users).

VM servers 232-236 may notify VVM server 252 of new voicemail messagesby sending messages (e.g., SMPP messages) to VVM server 252 throughnotification server 260. VM servers 232-236 may also provide voicemailmessage information (e.g., voicemail message headers) to VVM server 252by sending messages (e.g., IMAP (Internet Message Mapping Protocol)messages) to VVM server 252 through VVM gateway 262. VM servers 232-236may also send voicemail message audio files to devices 208-220 throughVVM gateway 262, VVM server 252 and/or device proxy 254, for example.

SWD server 238 may include a database of device numbers (e.g., phonenumbers, mobile device numbers, Universal Resource Indicators (URIs), orUniversal Resource Locaters (URLs)) and corresponding mailboxidentifiers (mailbox IDs) associated with each of the device numbers. Amailbox ID may identify the mailbox used for storing voicemail messagesfor a corresponding device number. A mailbox ID may also identify the VMserver (e.g., one of VM servers 232-236) with which the mailbox isassociated. SWD 238 may also store information for associating multipleuser devices, device numbers, or mailbox IDs with a single user, such asassociating user devices 208-220 with the same user.

VVM server 252 may include one or more computer systems for hostingprograms, databases, and/or applications. VVM server 252 may run a webserver application, such as Apache, to serve web pages when requested.For example, VVM server 252 may allow a user to access voicemail messageover the a data network, for example, using computer 208. VVM server 252may request voicemail messages and/or headers from one of VM servers232-236 and may forward voicemail messages and/or headers to any one ofdevices 208-220 directly or through VVM gateway 262, device proxy 254,and/or SMPP gateway 256.

Notification server 260 may receive voicemail message notifications(e.g., SMPP messages) from VM servers 232-236. Notification server 260may pass notifications of voicemail messages received from VM servers232-236 to VVM server 252 (e.g., as HTTP messages).

VVM gateway 262 may receive information about voicemail messages (e.g.,voicemail message headers) from VM servers 232-236. The information mayinclude lists of voicemail messages that may include data conforming to,for example, the IMAP protocol. VVM gateway 262 may pass voicemailmessage headers received from VM servers 232-236 to VVM server 252. VVMgateway 262 may pass data to VVM server 252 in the form of XML(eXtensible Markup Language) data in HTTP messages, for example.

Device proxy 254 may receive communications from one or more userdevices 210-220 for forwarding to other devices (e.g., VVM server 252and/or SMPP gateway 256). Device proxy 254 may also authenticate userdevices (e.g., user devices 210-220) by, for example, communicating withauthentication server 258. Authentication server 258 may storeinformation related to device authentication, such as session cookies.Device proxy 254 may communicate with devices (e.g., user devices210-220) using secure channels implementing, for example, SSL (SecureSocket Layer) protocols or TLS (Transport Layer Security) protocols.

SMPP gateway 256 may receive SMPP (e.g., SMS (Short Message System))messages from device proxy 254 and pass the received SMPP messages touser devices, such as user devices 216-220. SMPP gateway 256 may alsoreceive SMPP messages from user devices 216-220, for example, and passthe received SMPP messages to device proxy 254.

In other embodiments, network 200 may include more, fewer, or differentdevices. Moreover, one or more devices 208-262 may perform one or morefunctions of any other device in network 200. Furthermore, one or moreof devices 208-262 may be remotely located from each other, e.g.,devices 208-262 may be geographically diverse. Although FIG. 2 showsdevices 208-262 coupled to each other in a particular configuration,devices 208-262 may also be arranged in other configurations, eithercoupling directly with each other or through one or more networks, suchthat any one of devices 208-262 may communicate with any other one ofdevices 208-262. For example, any one of devices 208-262 may communicatewith any other one of devices 208-262 through the Internet, an ad hocnetwork, a local area network (LAN), a wide area network (WAN), ametropolitan area network (MAN), a cellular network, a PSTN, ahigh-speed fiber optic network (e.g., FiOS™), or any other network orcombinations of networks.

FIG. 3 is diagram of an exemplary user device 300, such as one or moreof user devices 208-220. As illustrated, user device 300 may include aspeaker 304, a display 306, control keys 308, a keypad 310, and amicrophone 312. User device 300 may include other components (not shownin FIG. 3) that aid in receiving, transmitting, and/or processing data.Moreover, other configurations of user device 300 are possible.

Speaker 304 may provide audible information to a user of user device300. Display 306 may include a display screen to provide visualinformation to the user, such as video images or pictures, and mayinclude a touch-screen display to accept inputs from the user. Forexample, display 306 may provide information regarding incoming oroutgoing telephone calls, telephone numbers, contact information,current time, voicemail, email, etc. Display 306 may display the GUIsshown in FIGS. 1B-1D, for example.

Control keys 308 may permit the user to interact with user device 300 tocause user device 300 to perform one or more operations, such asinteracting with a visual voicemail application. Control keys 308 mayinclude soft keys that may perform the functions indicated on display306 directly above the keys. Keypad 310 may include a standard telephonekeypad and may include additional keys to enable inputting (e.g.,typing) information into user device 300. Microphone 312 may receiveaudible information from the user.

FIG. 4 is a block diagram of exemplary components of a client computingmodule 400. User devices 208-220 may each include one or more computingmodules 400. Client computing module 400 may include a bus 410,processing logic 420, an input device 430, an output device 440, acommunication interface 450, and a memory 460. Client computing module400 may include other components (not shown) that aid in receiving,transmitting, and/or processing data. Moreover, other configurations ofcomponents in client computing module 400 are possible.

Bus 410 may include a path that permits communication among thecomponents of client computing module 400. Processing logic 420 mayinclude any type of processor or microprocessor (or groups of processorsor microprocessors) that interprets and executes instructions. In otherembodiments, processing logic 420 may include an application-specificintegrated circuit (ASIC), a field-programmable gate array (FPGA), orthe like.

Input device 430 may include a device that permits a user to inputinformation into client computing module 400, such as a keyboard (e.g.,control keys 308 and/or keypad 310), a mouse, a pen, a microphone (e.g.,microphone 312), a remote control, a touch-screen display (e.g., display306), etc. Input device 430 may include an accelerometer that may allowclient computing module to measure acceleration and movement of thedevice that includes the client computing module. Output device 440 mayinclude a device that outputs information to the user, such as a display(e.g., display 306), a printer, a speaker (e.g., speaker 304), etc.Output device 440 may also include a vibrator to alert a user.

Input device 430 and output device 440 may allow the user to activate aparticular service or application, such as a visual voicemailapplication and/or service. Input device 430 and output device 440 mayallow the user to receive and view a menu of options and select from themenu options. The menu may allow the user to select various functions orservices associated with applications executed by client computingmodule 400.

Communication interface 450 may include any transceiver-like mechanismthat enables client computing module 400 to communicate with otherdevices and/or systems. Communication interface 450 may include atransmitter that may convert baseband signals to radio frequency (RF)signals and/or a receiver that may convert RF signals to basebandsignals. Alternatively, communication interface 450 may include atransceiver to perform functions of both a transmitter and a receiver.Communication interface 450 may be coupled to an antenna fortransmission and reception of the RF signals. Communications interface450 may include a network interface card, e.g., Ethernet card, for wiredcommunications or a wireless network interface (e.g., a WiFi) card forwireless communications. Communication interface 450 may also include,for example, a universal serial bus (USB) port for communications over acable, a Bluetooth™ wireless interface for communicating with Bluetoothdevices, a near-field communication (NFC) interface, etc. Communicationinterface 450 may implement a wireless communication protocol, e.g.,GSM, CDMA, WCDMA, GPRS, EDGE, etc. Communications interface 450 may alsoreceive, transmit and/or process digital or analog audio inputs/outputsand/or digital or analog video inputs/outputs.

Memory 460 may include a random access memory (RAM) or another type ofdynamic storage device that may store information and instructions,e.g., an application, for execution by processing logic 420; a read-onlymemory (ROM) device or another type of static storage device that maystore static information and instructions for use by processing logic420; and/or some other type of magnetic or optical recording medium andits corresponding drive, e.g., a hard disk drive (HDD), for storinginformation and/or instructions.

Memory 460 may include a VVM application 462, a voicemail message table464 (e.g., database), and voicemail audio files 466. VVM application 462may allow a user to receive, select, listen to, and act on (e.g., save,forward, delete) voicemail messages. Message table 464 may store a listof voicemail messages including information such as the date and time ofa voicemail message, the duration of the message, the status of themessage, etc. Voicemail audio files 466 may include the audio data ofthe voicemails (e.g., in any format, including MP3, WMA (Windows MediaAudio), AAC (Advanced Audio Coding), QCP (Qualcomm Code Predictionand/or Qualcomm Code Excited Linear Prediction), Ogg Vorbis, etc.).

Client computing module 400 may perform certain operations, as describedbelow. Client computing module 400 may perform these operations inresponse to processing logic 420 executing software instructionscontained in a computer-readable medium, such as memory 460. Acomputer-readable medium may be defined as a physical or logical memorydevice. The software instructions may be read into memory 460 fromanother computer-readable medium or from another device viacommunication interface 450. The software instructions contained inmemory 460 may cause processing logic 420 to perform processes that aredescribed below.

FIG. 5 is a block diagram of exemplary components of a server computingmodule 500. Devices 232-262 may include one or more server computingmodules (e.g., a rack of server computer modules), such as computingmodule 500. Server computing module 500 may include a bus 510,processing logic 520, a communication interface 550, and a memory 560.Server computing module 500 may include other components (not shown)that aid in receiving, transmitting, and/or processing data. Moreover,other configurations of components in module 500 are possible.

Bus 510 may include a path that permits communication among thecomponents of module 500. Processing logic 520 may include any type ofprocessor or microprocessor (or groups of processors or microprocessors)that interprets and executes instructions. In other embodiments,processing logic 520 may include an ASIC, an FPGA, or the like.

Communication interface 550 may include any transceiver-like mechanismthat enables module 500 to communicate with other devices and/orsystems. Communication interface 550 may include a transmitter that mayconvert baseband signals from processing logic 520 to RF signals and/ora receiver that may convert RF signals to baseband signals.Alternatively, communication interface 550 may include a transceiver toperform functions of both a transmitter and a receiver. Communicationinterface 550 may be coupled to an antenna for transmission andreception of the RF signals. Communications interface 550 may include anetwork interface card, e.g., Ethernet card, for wired communications ora wireless network interface (e.g., a WiFi card) for wirelesscommunications. Communication interface 550 may also include, forexample, a USB port for communications over a cable, a Bluetoothwireless interface for communicating with Bluetooth devices, a NFCinterface, etc. Communication interface 550 may implement a wirelesscommunication protocol, e.g., GSM, CDMA, WCDMA, GPRS, EDGE, etc.Communications interface 550 may receive, transmit and/or processdigital or analog audio inputs/outputs and/or digital or analog videoinputs/outputs.

Memory 560 may include a RAM or another type of dynamic storage devicethat may store information and instructions, e.g., an application 562and application data 564, for execution by processing logic 520; a ROMdevice or another type of static storage device that may store staticinformation and instructions for use by processing logic 520; and/orsome other type of magnetic or optical recording medium and itscorresponding drive, e.g., a HDD, for storing information and/orinstructions.

In the case of VM servers 232-236, for example, application 562 mayinclude an application to receive voicemail messages on behalf of userdevices, such as user devices 216-220, when the users of the devices donot answer call requests, for example. Application data 564 may includevoicemail message tables and corresponding audio data.

In the case of VVM server 252, for example, application 562 may includean application to receive voicemail message information andcorresponding voicemail audio data from VM servers 232-236 and deliverthe received voicemail message information and corresponding voicemailaudio data to user devices. As such, in the case of VVM server 252,application data 564 may also include voicemail message tables andcorresponding audio files.

Module 500 may perform certain operations, as described in detail below.Module 500 may perform these operations in response to processing logic520 executing software instructions contained in a computer-readablemedium, such as memory 560. The software instructions may be read intomemory 560 from another computer-readable medium or from another devicevia communication interface 550. The software instructions contained inmemory 560 may cause processing logic 520 to perform processes that aredescribed below.

FIG. 6A is a diagram of exemplary message tables 600-1, 600-2, and600-3, e.g., databases (collectively “message tables 600”). Messagetables 600 may each store information related to voicemail messages.Each entry (e.g., record) in message tables 600 may include informationregarding a different voicemail message.

Message tables 600 may be stored in one or more of VM servers 232-236(e.g., in memory 560). In one exemplary embodiment, message table 600-1may store information regarding messages associated with smart phone216; message table 600-2 may store information regarding messagesassociated with PDA 218; and message table 600-3 may store informationregarding messages associated with mobile phone 220. In this exemplaryembodiment, message table 600-1 may be stored in work VM server 232;message table 600-2 may be stored in home VM server 234; and messagetable 600-3 may be stored in wireless VM server 236. In otherembodiments, message tables 600 may also be stored in another device innetwork 200, such as in VVM server 252 (e.g., in memory 560) or any ofdevices 208-220 (e.g., in memory 460 as message table 464).

Message tables 600 may include a mailbox identifier (“mailbox ID” or“MBID”) field 602, a message identifier (“message ID” or “MID”) field604, a called device number (DN) field 605, a caller DN field 606, astate field 610, and a location field 612.

Mailbox ID field 602 may include a value identifying a mailbox in one ofVM servers 232-236. In exemplary message tables 600, there are threemailboxes identified in mailbox ID field 602: MBA1, MBB1, and MBC1. Inthis example, MBA1 may be a mailbox in work VM server 232 associatedwith smart phone 216, MBB1 may be a mailbox in home VM server 234associated with PDA 218 and, and MBC1 may be a mailbox in wireless VMserver 236 associated with mobile phone 220.

Message ID field 604 may include a value that may uniquely identify avoicemail message in a mailbox. For example, record 652 in message table600-1 stores a message identifier of A124 in message ID field 604.

Called DN field 605 may include a device number (e.g., phone number,mobile device number, URI, or URL) of the user device for which thecorresponding voicemail message is intended. In exemplary message tables600, there are three device numbers in called DN field 605: 2022513434,7035678989, and 2023459292. In this example, the device number2022513434 may be associated with mobile phone 220; the device number2023459292 may be associated with PDA 218; and the device number7035678989 may be associated with smart phone 216. In one embodiment,there may be a one-to-one relationship between a called DN and a mailboxID, such that each called DN is associated with one mailbox ID and viceversa.

Caller DN field 606 may include a device number (e.g., phone number,mobile device number, URI, or URL) of the user device associated withthe depositing of the corresponding voicemail message. In exemplarymessage tables 600, the messages identified in records 652-656 weredeposited by various different device numbers as indicated in field 606.

State field 610 may include one or more tags identifying the state(e.g., status) of the corresponding voicemail message. Tags in statefield 610 may include NEW, HEARD, SAVED, and DELETED. The NEW tag mayindicate a voicemail message that has not been listened to yet by theuser. The HEARD tag may indicate a voicemail message that has beenlistened to by the user. The SAVED tag may indicate a voicemail messagethat the user requested be saved in one of user devices 208-220 and/orone of VM servers 232-236 for a number of days, e.g., 21 days. TheDELETED tag may indicate a voicemail message that has been marked fordeletion by, for example, a user device. Other tags in state field 610are possible, such as BUSINESS to identify business voicemail message,PERSONAL to identify personal voicemail message, FAMILY to identifyvoicemail message from family members, URGENT to identify urgentmessages, and NOT URGENT to identify non-urgent messages.

Location field 612 may indicate the location (e.g., filename and/orpathname, URL, or URI) of an audio file associated with thecorresponding voicemail message. In one embodiment, the audio file maybe stored locally and location field 612 may include the filename of thelocal file associated with the corresponding voicemail message. Inanother embodiment, the audio file may be stored remotely and locationfield 612 may include the remote location of the audio file associatedwith the corresponding voicemail message.

Message tables 600 may include additional, different, or fewer fieldsthan illustrated in FIG. 6A. For example, message tables 600 may includea call time field that may include the date and time that thecorresponding voicemail message was left in one of VM servers 232-236.As another example, message tables 600 may include a priority field thatmay specify the urgency (e.g., 1-10) of the corresponding voicemailmessage.

FIG. 6B is a block diagram of exemplary message tables 600-1′, 600-2′,and 600-3′ (collectively message tables 600′). Message tables 600-1′,600-2′, and 600-3′ may represent message tables 600-1, 600-2, and 600-3,respectively, but at a different point in time. Message tables 600′ maybe referred to as “updated message tables 600′.” Like exemplary messagetables 600, exemplary message tables 600′ include records 652, 654, and656. Unlike message tables 600, however, message tables 600′ includerecords 658, 660, and 662. In particular, message table 600-1′ includesrecord 662 that does not appear in message table 600-1; message table600-2′ includes record 658 that does not appear in message table 600-2;and message table 600-3′ includes record 660 that does not appear inmessage table 600-3. As shown in exemplary message tables 600′, records658, 660, and 662 each include a state of NEW in state field 610.

The data in message tables 600 and 600′ are for exemplary purposes only.As shown, for example, message tables 600-1 and 600-1′ store informationfor only one mailbox ID and one called DN (e.g., mailbox ID of MBA1 andcalled DN of 7035678989). Message tables 600-1 and 600-1′ (and the othermessage tables) may store information for more than one mailbox ID andcalled DN, however. In addition, message tables 600 and 600′ may storethousands or hundreds of thousands of records.

FIG. 7A is a block diagram of an exemplary aggregate message table 700,e.g., a database. Aggregate message table 700 may store information fromone or more other message tables, such as message tables 600. Aggregatemessage table 700 may be stored in one or more of devices 208-220 (e.g.,in memory 460 as message table 464). Aggregate message table 700 mayalso be stored in VVM server 252 (e.g., in memory 560) or another devicein network 200.

Like message tables 600, each entry in aggregate message table 700 mayinclude information regarding a different voicemail message. Further,aggregate message table 700 may include the same or similar fields asmessage tables 600. That is, aggregate message table 700 may include amailbox ID field 702, a message ID field 704, a called DN field 705, acaller DN field 706, a state field 710, and a location field 712.Aggregate message table 700 may include additional, different, or fewerfields than illustrated in FIG. 7. These fields shown in FIG. 7 maystore the same or similar information as descried above for fields602-612 in FIG. 6A of message tables 600 or 600′.

Exemplary aggregate message table 700 may include records 752, 754, and756, which may store the same information as records 652, 654, and 656,respectively, in message tables 600. Thus, aggregate message table 700may be considered an “aggregate” table because it aggregates messageinformation from a group of disparate message tables corresponding todifferent mailboxes, in this case message tables 600. In an alternativeembodiment, message table 700 may store data from only one other messagetable.

FIG. 7B is a block diagram of an exemplary aggregate message table 700′,which may represent aggregate message table 700 at a different point intime. Aggregate message table 700′ includes records 752, 754, and 756that also appear in aggregate message table 700. Aggregate message table700′ also includes records 758, 760, and 762 that do not appear inaggregate message table 700. Exemplary aggregate message table 700′ mayinclude records 758, 760, and 762, which may store the same informationas records 658, 660, and 662, respectively, in message tables 600′. Asshown, records 758, 760, and 762 each include a state of NEW in statefield 710.

The data in aggregate message tables 700 and 700′ are for exemplarypurposes. Aggregate message tables 700 and 700′ as shown, for example,store information for voicemail messages associated with a single user,e.g., the user related to smart phone 216, PDA 218, and mobile phone220. Aggregate message tables 700 and 700′ may store informationassociated with thousands even hundreds of thousands of users. Inaddition, aggregate message tables 700 and 700′ may store thousands orhundreds of thousands of messages, for example.

FIG. 8 is a block diagram of an exemplary notification table 800.Notification table 800 may store information identifying the userdevice(s) that are to receive a notification when, for example, avoicemail message is received for a particular mailbox. Notificationtable 800 may be stored in SWD server 238 (e.g., in memory 560).Alternatively or additionally, notification table 800 may be stored inVVM server 252 or in another device in network 200. In one embodiment, auser may edit and update information stored in notification table 800using, for example, a browser in computer 208.

Notification table 800 may include a mailbox ID field 602 and anotification DN field 804. Notification table 800 may includeadditional, different, or fewer fields than illustrated in FIG. 8.

Mailbox ID field 802 may include a value identifying a mailbox in one ofthe VM servers, such as one of VM servers 232-236. In exemplarynotification table 800, there are three mailboxes identified in mailboxID field 602: MBA1, MBB1, and MBC1. These three mailboxes correspond tothe mailboxes stored in message tables 600 and aggregate message table700, for example.

Notification DN field 804 may include the device number(s) (e.g., phonenumber, mobile device number, URI, or URL) of the user device(s)associated with the corresponding mailbox in mailbox ID field 802 forreceiving voicemail message information notifications. As indicated innotification table 800, fields 802 and 804, when mailbox MBC1 receives anew voicemail, for example, then the user device associated with devicenumbers 2022513434, 7035678989, and 2023459292 (e.g., mobile phone 220,smart phone 216, and PDA 218, respectively) may be notified.

As indicated above, notification table 800 may include additional,different, or fewer fields than illustrated in FIG. 8. For example,notification table 800 may include fields that indicate what type ofnotification messages (e.g., only new messages) should be sent todifferent devices and when they should be sent.

FIG. 9A is a flowchart of an exemplary process 900A for receiving avoicemail message and for notifying a VVM server of voicemailinformation. FIG. 9A is described with respect to FIG. 10, which is adiagram of exemplary network signals for notifying a user device ofvoicemail information. For the purposes of FIG. 10, device proxy 254,SMPP gateway 256, notification server 260, and VVM gateway 262 have beenomitted for simplicity. All or parts of process 900A may run in work VMserver 232, home VM server 234, wireless VM server 236, VVM server 252,and/or any of user devices 208-220.

Process 900A may begin when a new voicemail message is received (block902). For example, mobile phone 220 (e.g., device number 2022513434) mayreceive a call request from another device (e.g., device number4569812124). Mobile phone 220, however, may not accept (e.g., notanswer) the call request, which may cause the call request to bedirected to wireless VM server 236, and wireless VM server 236 mayreceive a voicemail message. A message table may be updated (block 903).Wireless VM server 236 may associate the received voicemail message witha message ID (e.g., a message ID of C130), the called DN (e.g.,2022513434), and the caller DN (e.g., 4569812124) and wireless VM server236 may store this information in its message table, e.g., message table600-3. In this example, wireless VM server 236 may update message table600-3 to include record 660, as shown in message table 600-3′. WirelessVM server 236 may also store the mailbox ID (e.g., MBC1), the state(e.g., NEW), and the filename of the audio data (e.g., MSG4.QCP) inrecord 660.

Notification of voicemail message information may be sent (block 904).Having received a new voicemail (e.g., the voicemail message associatedwith record 660), wireless VM server 236 may send a notification (signal1002) to VVM server 252 of the new voicemail. The notification message(signal 1002) may include the called DN, e.g., 2022513434 from field605, and the mailbox ID, e.g., MBC1 from mailbox ID field 602. WirelessVM server 236 may send the notification (signal 1002) to VVM server 252through notification server 260 (shown in FIG. 2), for example. In oneembodiment, the notification message (signal 1002) may include an SMPPmessage. In one embodiment, the change of the message table in the VMserver (e.g., the addition of record 660 to message table 600-3′ inwireless VM server 236) may prompt the sending of the notificationmessage (signal 1002). In this example, the notification of voicemailmessage information may be the result of a new voicemail message.Notifications may also be sent for other reasons, such as a state changein state field 610 of a voicemail message. In another embodiment,notification messages, such as signal 1002, may additionally oralternatively be sent on a periodic basis.

The notification of voicemail message information may be received (block905). VVM server 252 may receive the notification (signal 1002) ofvoicemail message information. Voicemail message information may berequested (block 906). In response to signal 1002, VVM server 252 maysend a request (signal 1004) for information regarding the voicemailmessages stored by wireless VM server 236. VVM server 252 may send therequest (signal 1004) to wireless VM server 236 through VVM gateway 262(shown in FIG. 2), for example. The request (signal 1004) may includethe called DN (e.g., of mobile phone 220 received earlier in signal1002), the mailbox ID (e.g., MBC1 received earlier in signal 1002), anda personal identification number (PIN) associated with the mailbox ID.In one embodiment, if VVM server 252 does not store the PIN associatedwith the mailbox ID, then VVM server 252 may request the PIN from mobilephone 220.

Information regarding voicemail messages may be received (block 908).VVM server 252 may receive voicemail message information (signal 1006)from wireless VM server 236. Wireless VM server 236 may send voicemailmessage information (signal 1006) in response to receiving the request(signal 1004) for information regarding voicemail messages. Wireless VMserver 236 may send the information (signal 1006) to VVM server 252through VVM gateway 262 (shown in FIG. 2), for example. The voicemailmessage information (signal 1006) may include a list of voicemailmessages. In one embodiment, the information may include XML formatteddata including message IDs and the corresponding state (e.g., theinformation stored in state field 610).

In the current example where mobile phone 220 receives a voicemailmessage, the information in signal 1006 may include the message IDs ofC129 and C130 from message ID field 604. The information in signal 1006may also include the states associated with the two messages, e.g., NEWfor the voicemail message associated with message ID C130 (record 660)and HEARD for the voicemail message associated with message ID C129(record 654). In one embodiment, signal 1006 may include informationrelated to only the records that prompted notification signal 1002 inthe first place, e.g., the records that are new or have changedinformation.

VVM server 252 may update an aggregate message table (block 909). Forexample, before receiving the information (signal 1006) regardingvoicemail messages, VVM server 252 may store an aggregate message table(similar to aggregate message table 700) which does not include a recordcorresponding to the information in record 660 of message table 600-3′of FIG. 6B. After receiving the information (signal 1006) regardingvoicemail messages, VVM server 252 may update its aggregate messagetable to include the information in record 760 as shown in aggregatemessage table 700′, which corresponds to record 660 of message table600-3′, e.g., the information of which was received in signal 1006.

In another embodiment, VVM server 252 may request voicemail messageinformation (e.g., by sending signal 1004) on a periodic basis inaddition to or alternatively to waiting for a notification (e.g., signal1002). In this embodiment, VVM server 252 may periodically requestvoicemail message information from each VM server, such as VM servers232-236.

Work VM server 232 and home VM server 234 may also implement portions ofprocess 900A. For example, home VM server 234 may receive a voicemailmessage (block 902) for an unanswered call to PDA 218. Informationregarding this voicemail may be stored (block 903) as record 658 inmessage table 600-2′. Home VM server 234 may send a notification signal(similar to signal 1002) to VVM server 252 (block 904). VVM server 252may request (block 906) and receive (block 908) voicemail informationfrom home VM server 234. VVM server 252 may update (block 909) itsaggregate message table to include the information in record 758 (theinformation received from home VM server 234), as shown in exemplaryaggregate message table 700′.

Work VM server 232 may also receive a voicemail message (block 902) foran unanswered call to smart phone 220. Information regarding thisvoicemail may be stored (block 903) as record 662 in message table600-1′. Work VM server 232 may send a notification signal (similar tosignal 1002) to VVM server 252 (block 904). VVM server 252 may request(block 906) and may receive (block 908) voicemail information from workVM server 232. VVM server 252 may update its aggregate voicemail messagetable to include the information in record 762 as shown in aggregatemessage table 700′.

As shown, in response to a voicemail message left in each of VM servers232-236, aggregate message table stored in VVM server 252 may be updatedfrom the condition shown in exemplary message table 700 to that shown inshown in aggregate message table 700′. The aggregate message tablestored in VVM server 252 may then reflect the current state of messagesfrom the many VM servers, such as work VM server 232, home VM server234, and wireless VM server 236.

FIG. 9B is a flowchart of an exemplary process 900B for notifying a userdevice of voicemail message information. FIG. 9B is also described withrespect to FIG. 10. Process 900B may begin when VVM server 252 updatesits aggregate message table, such as aggregate message table 700. Forexample, as discussed above with respect to process 900A, VVM server 252may have updated its aggregate message from the condition shown inaggregate table 700 to the state shown in updated aggregated messagetable 700′ (e.g., to add record 760 associated with mailbox MBC1). Ifthe aggregate message table has been updated (block 952: YES), then anotification table may be queried (block 954). VVM server 252 may querynotification table 800 stored in SWD server 238 to determine which userdevices should be notified of the change to the aggregate message table.In this example, as indicated in notification table 800, a notificationfor a new voicemail in mailbox MBC1 may be sent to the user deviceassociated with device number 2022513434 (e.g., mobile phone 220), theuser device associated with device number 7035678989 (e.g., smart phone216), and the user device associated with device number 2023459292(e.g., PDA 218).

One or more user devices may be notified (block 958). Exemplarynotification messages are shown in FIG. 10, where VVM server 252 sendsnotification messages (signals 1008, 1010, and 1012) to mobile phone220, PDA 118, and smart phone 216 (e.g., through device proxy 254 and/orSMPP gateway 256, shown in FIG. 2). In one embodiment, signals 1008through 1012 may all include the same or similar information.

In one embodiment, the notification (e.g., signal 1008) may include, fora particular mailbox ID, the number of voicemail messages (#VM), thenumber of new messages (#NEW), and the message ID of the most recent newvoicemail message. The notification (e.g., signal 1008) may also includethe mailbox ID to which the notification signal corresponds (e.g., themailbox ID associated with the change in the aggregate message tablethat may have resulted in the notification message). In one embodiment,the notification (e.g., signal 1008) may also include the message IDs ofall the voicemail messages currently in the mailbox.

In one embodiment, VVM server 252 may send the notification to userdevice(s) in an order specified by a user in notification table 800. Inanother embodiment, VVM server 252 may send the notification first tothe user device currently being used as measured by an accelerometer,for example. In yet another embodiment, VVM server 252 may determinewhich device is currently being used based on presence informationstored in the user device, for example.

In one embodiment, the notification (e.g., signal 1008) may include anSMS message. In this embodiment, the SMS message (e.g., signal 1008) mayinclude a BREW (Binary Run Time Environment for Wireless) applicationmessage in an SMS message. In another embodiment, the SMS message (e.g.,signal 1008) may include a MWI (Mail Waiting Indicator) message.

After sending notifications (block 958), process 900B may return toblock 952. In addition, if there has been no update to the aggregatemessage table (block 952: NO), then process 900B may pause (block 956)and may return to block 952.

As shown above with respect to process 900A, VVM server 252 may updateits aggregate message table for mailboxes MBB1 and MBA1, as well asMBC1. These updates may also prompt a query to notification table 800(block 954) and notifications being sent (block 958). In one embodiment,a notification (e.g., signal 1008) may include information for a groupof mailbox IDs, such as MBB1, MBA1, and MBC1. For example, anotification signal may include, for a group of mailbox IDs, the numberof voicemail messages (#VM) for each mailbox ID, the number of newmessages (#NEW) for each mailbox ID, and the message ID of the mostrecent new voicemail message for each mailbox ID. In this embodiment,the notification (e.g., signal 1008) may also include the mailbox IDs towhich the notification signal corresponds.

After receiving notification of voicemail messages, a user device maydetermine to download some or all of the voicemail message informationidentified in the notification. FIG. 11 is a flowchart of a process 1100for receiving voicemail message information. All or parts of process1100 may be performed by a user device, such as one of user devices208-220, VVM server 252, or another device in network 200. Process 1100is described with respect to FIG. 10 and FIG. 12, which are diagrams ofexemplary network signals passed in network 200 for receiving avoicemail message and/or authenticating a user device. For the purposesof FIG. 12, device proxy 254, SMPP gateway 256, notification server 260,and VVM gateway 262 have been omitted for simplicity.

Process 1100 may start when a user device receives a notificationmessage, e.g., signal 1008 (block 916). In one embodiment, thenotification (signal 1008) may trigger the launching of VVM application462. For example, the notification (signal 1008) may trigger the userdevice to perform process 1100.

A determination of whether to synchronize may be made (block 1104). Forexample, mobile phone 220 may receive the notification message (signal1008) and may compare the information in the notification message(signal 1008) with information already stored in mobile phone 220.Mobile phone 220 may determine that it does not have the most recentvoicemail message information (block 1104: YES) and may initiate asynchronization with VVM server 252 to receive the most recent voicemailinformation.

In one embodiment, the user device, e.g., mobile phone 220, maydetermine whether to synchronize or not based, for a particular mailboxID, for example, on the number of unheard (e.g., new) messages, thetotal number of messages, and/or the newest message ID. In yet anotherembodiment, the user device, e.g., mobile phone 220, may determinewhether to synchronize or not based, for a group of mailbox IDs, forexample, on the number of unheard messages, the total number ofmessages, and/or the newest message IDs for the group of mailbox IDs. Inanother embodiment, the user device, e.g., mobile phone 220, maydetermine whether to synchronize or not based, for a particular mailboxID, only on this information (i.e., the number of unheard messages, thetotal number of messages, and/or the newest message ID). Further, theuser device, e.g., mobile phone 220, may determine whether tosynchronize or not based, for a group of mailbox IDs, only on thisinformation (i.e., the number of unheard messages, the total number ofmessages, and/or the newest message IDs for the group of mailbox IDs).In another embodiment, mobile phone 220 may determine whether tosynchronize or not based on additional information, such as the fulllist of voicemail message IDs.

The notification (e.g., signal 1008) may include a message that thedevice should synchronize, without necessarily specifying any otherinformation. In another embodiment, mobile phone 220 may determinewhether to synchronize on a periodic basis no matter the information inthe notification (signal 1008).

If the notification message (signal 1008), for example, includes a mostrecent message ID of which mobile phone 220 is unaware, then mobilephone 220 may decide to synchronize (block 1104: YES). If thenotification message (signal 1008) indicates that the number of unheardmessages is different than the information stored in mobile phone 220,then mobile phone 220 may decide to synchronize (block 1104: YES). Ifthe notification message (signal 1008) indicates that the total numberof messages is different than the information stored in mobile phone220, then mobile phone 220 may decide to synchronize (block 1104: YES).In one embodiment, mobile phone 220 may display the number of unheard(e.g., new) voicemail messages and the total number of voicemailmessages to the user of mobile phone 220.

For example, mobile phone 220 may include an aggregate message table inthe state shown in aggregate message table 700, whereas VVM server 252may include an aggregate message table in the state shown in aggregatemessage table 700′. The notification message (signal 1008) sent from VVMserver 252 to mobile phone 220 may include information regardingaggregate message table 700′, such as the total number of voicemailmessages (e.g., 2 for mailbox ID of MBC1), the number of new voicemailmessages (1 for mailbox ID of MBC1), and the most recent message ID(e.g., C130 for mailbox ID of MBC1). Mobile phone 220 may determine thatsynchronization should be performed because, comparing the receivedinformation (signal 1008) to the information in its aggregate messagetable (in the state shown in table 700), mobile phone 220 may haveincomplete information. For example, the aggregate message table inmobile phone 220 would suggest the number of voicemail messages would be1 (not 2) and there are no new voicemail messages (rather than 1). Inone embodiment, the notification (signal 1008) may include threeseparate signals, e.g., one for each mailbox ID.

If the user device does not synchronize (block 1104: NO), then process1100 may return to block 1102. If the user device decides to synchronize(block 1104: YES), then a login or connection request may be sent (block1106). For example, mobile phone 220 may send a connection request(signal 1202) to VVM server 252 and/or device proxy 254. The connectionrequest may be received (block 1108). For example, the connectionrequest (signal 1202) sent by mobile phone 220 may be received by VVMserver 252 and/or device proxy 254. In one embodiment, the connectionrequest (signal 1202) may include a request for voicemail messageheaders (e.g., a list of voicemail messages). The request for aconnection (signal 1202) may include the device number (e.g., for mobilephone 220), the mailbox ID, and/or a PIN. In one embodiment, the user ofmobile phone 220 may be prompted for the PIN and/or the PIN may bestored in mobile phone 220 and automatically provided.

The user device may be authenticated (block 1110). To authenticate theuser device, such as mobile phone 220, VVM server 252 and/or deviceproxy 254 may send a PIN validation query (signal 1204) to wireless VMserver 236. The PIN validation query (signal 1204) may include the PINand mailbox ID received from the user device, e.g., mobile phone 220, inthe login request (signal 1202). Wireless VM server 236 may determinewhether the PIN validation message (signal 1204) includes the correctPIN for the device number and mailbox combination. If the PIN validationmessage (signal 1204) includes the correct PIN, then a confirmationmessage (signal 1206) may indicate a successful user validation. If thePIN validation message (signal 1204) does not include the correct PIN,then confirmation message (signal 1206) may indicate a failed uservalidation (e.g., failed authentication). If successful, VVM server 252and/or device proxy 254 may store the PIN, the mailbox ID, and thedevice number for subsequent communications with VM servers 232-236.

A cookie may be sent (block 1112). After successful authentication, VVMserver 252 and/or device proxy 254 may respond to mobile phone 220 witha login response message (signal 1208). The login response message(signal 1208) may include the device number of mobile phone 220, mailboxID of mobile phone 220, and a session cookie. In one embodiment, thesession cookie may include an expiration time or be associated with anexpiration time. For example, the session cookie may expire afterfifteen minutes, one half of an hour, an hour, etc. In one embodiment,authentication server 258 may provide VVM server 252 and/or device proxy254 with the session cookie for forwarding to mobile phone 220. In oneembodiment, the session cookie may be used by mobile phone 220 in futurecommunications to authenticate mobile phone 220. In one embodiment, VVMserver 252 and/or device proxy 254 may communicate with authenticationserver 258 to validate any cookies received from mobile phone 220.

In one embodiment, if the user device, such as mobile phone 220, doesnot receive a response (signal 1208), then the user device may be in anenvironment where data transfers are not possible. In this situation,the user device may implement the traditional user interface (TUI) forreceiving voicemail message, such as requiring the user to call one ofVM servers 232-236. In this situation, the user may use the user deviceto call one of VM servers 232-236 directly through the TUI.

A list of voicemail messages may be sent (block 1114). For example, VVMserver 252 may send a list of voicemail message headers (signal 1208).In one embodiment, the voicemail headers may include message IDs,mailbox IDs, caller device numbers, and the states of the messages(e.g., information stored in a message table). In one embodiment, thevoicemail headers may be sent using XML data formatting.

For example, the voicemail message headers (signal 1208) sent to mobilephone 220 from VVM server 252 may include records 752 through 762 ofaggregate message table 700. In one embodiment, signal 1208 may notinclude the audio files themselves (e.g., MSG*.QCP), but may include thenames of the audio files. In another embodiment, signal 1208 may includethe audio files themselves. In one embodiment, the voicemail messageheaders (signal 1208) sent to mobile phone 220 may include only therecords from the aggregate message table (in VVM server 252) that havenew or changed information. The voicemail message headers (signal 1208)may include headers only to those voicemail mailboxes for which the userdevice is configured to receive. For example, mobile phone 220 may beconfigured to receive message headers for mailboxes MBA1, MBB1, and MBC1as configured and stored in SWD 238.

The voicemail message list may be synchronized (block 1116). Mobilephone 220 may compare the voicemail message headers received in signal1208 with voicemail message information stored in mobile phone 220 andmay update its message table. For example, mobile phone 220 may updateits aggregate message table from the condition shown in message table700 to that shown in aggregate message table 700′. If mobile phone 220does not include a message table with any information, then mobile phone220 may create a message table corresponding to aggregate message table700′.

As a further example, if the voicemail message list (signal 1208)indicates that a particular message (identified by a message ID, forexample) has been deleted and mobile phone 220 does not previously knowthis information, then mobile phone 220 may indicate (by updatingmessage table) that the corresponding voicemail message has beendeleted. If the voicemail message list (signal 1208) indicates that aparticular message (identified by a message ID, for example) has beenheard and mobile phone 220 believed it to have been new, then mobilephone 220 may update its message table to indicate that the voicemailmessage has been heard.

Voicemail message audio files may be requested (block 1118). Forexample, mobile phone 220 may determine that the voicemail message listreceived indicates that a new voicemail audio file exists (e.g.,MSG9.QCP corresponding to record 762). Mobile phone 220 may not have thecorresponding audio file, e.g., mobile phone 220 may only have theheader information. In this situation, mobile phone 220 may send arequest message (signal 1212) for the audio file to VVM server 252. Therequest message (signal 1212) may include the device number (e.g., ofmobile phone 220), the session cookie from the earlier authentication,and the mailbox and message IDs for the requested voicemail audio file.In one embodiment, the request message (signal 1212) may include thefile format that the user device supports, such as QCP, MP3, AAC, OggVorbis, etc.

VVM server 252 may receive the request (signal 1212) and may send arequest (signal 1214) for the audio files to the appropriate one of VMservers 232-236 (block 1120). The request to wireless VM server 236(signal 1214) may include, for example, the device number (e.g., ofmobile phone 220), the PIN stored in device proxy 254 and/or VVM server252 after authentication, the message ID, the location, the requestedfile format (e.g., QCP), and the mailbox ID. In one embodiment, the userdevice requesting an audio file may be a different device than the userdevice associated with the mailbox ID. For example, mobile phone 220(associated with wireless VM server 236) may request an audio file fromhome VM server 234 or work VM server 232, as well as wireless VM server236.

Voicemail audio file(s) may be received and forwarded (block 1121). Forexample, VVM server 252 may receive the voicemail audio files (signal1216) and may forward the audio files (signal 1218) to mobile phone 220.One embodiment, mobile phone 220 may send multiple audio file requestmessages (e.g., signal 1212) for each new voicemail message mobile phone220 decides to download. In this embodiment, VVM server 252 may sendmultiple request messages (e.g., signal 1214) to wireless VM server 236,wireless VM server 236 may respond with multiple messages (e.g., signal1216), and VVM server 252 may send multiple audio files (e.g., signal1218) to mobile phone 220. In another embodiment, the audio file requestmessage (signal 1212) may include multiple mailbox and/or message IDs toidentify multiple audio files, e.g., an audio file associated with eachmessage ID. In one embodiment, mobile phone 220 may prompt the user ofthe device before sending an audio file request signal (signal 1212)because the user may not want to spend the time and/or bandwidth, forexample, to download multiple audio files.

The transmission of one or more voicemail audio files may be interrupted(block 1122). The user may interrupt the downloading of audio files byinterrupting the VVM device application, for example. In this situation(block 1122: YES), the downloading of voicemail messages may be stopped(block 1124) and a new voicemail notification message may display on theuser device, e.g., mobile phone 220 (block 1126). If the downloading ofaudio files is not interrupted (block 1122: NO), then a new voicemailnotification message may be displayed (block 1126) to the user aftersuccessful download of the audio files. An exemplary new voicemailnotification is shown in FIG. 1B, discussed above.

The voicemail message headers may be displayed (block 1128). Thevoicemail message headers may include the caller number, the callednumber, the mailbox ID, etc. An exemplary list of voicemail headers isshown in FIG. 1C, discussed above. In one embodiment, the voicemailmessage headers are displayed after the user acknowledges the newvoicemail message notification message in block 1126 by, for example,touching one of control keys 308 or display 306 on mobile phone 220.Voicemail messages may be displayed in order of when they were received,in order of urgency, etc.

A command to act on a voicemail message may be received (block 1130).For example, the user of mobile phone 220 may listen to a voicemailmessage, delete a voicemail message, save a voicemail message, etc. TheGUI shown in FIG. 1C, for example, includes buttons 114 and 116 fordeleting and playing a voicemail message, respectively.

One or more of user device 208-220 may similarly make a determination ofwhether to synchronize or not (block 1102). A user device may initiate asynchronization process at any time, such as when the device is turnedon, on a periodic basis, in response to a user action (e.g., selectionof a button on the user device), etc.

After a user device downloads voicemail message information, the usermay decide to listen to a voicemail message. FIG. 13 is a flowchart ofan exemplary process 1300 for listening to a voicemail message. Process1300 is described with respect to FIG. 14, which is a diagram ofexemplary network signals sent in network 200 for listening to avoicemail message. For the purposes of FIG. 14, device proxy 254, SMPPgateway 256, notification server 260, and VVM gateway 262 have beenomitted for simplicity.

Process 1300 may begin when a user of a device, such as mobile phone220, selects a message for listening to by, for example, using controlkeys 308, keypad 310, and/or touch-screen display 306. FIG. 1C shows aGUI for a user to input a command to listen to a message, for example. ALISTEN command may be received (block 1302). For example, a user device,such as mobile phone 220, may receive the LISTEN command from the userthrough the GUI shown in FIG. 1C. If the voicemail message audio file isin memory 460 of the user device (block 1304: YES), then the voicemailmessage may be played (block 1312). For example, mobile phone 220 mayhave already downloaded the voicemail message from wireless VM server236 in block 1121.

If the voicemail message audio file is not in memory 460 of the userdevice (block 1304: NO), then the user device may request the audio filecorresponding to the voicemail message. For example, mobile phone 220may not have the corresponding audio file in memory 460 if the userinterrupted the audio file download (FIG. 11, block 1122: YES) or if theuser opted not to download the audio files. In this case, in oneembodiment, mobile phone 220 may send an audio file request message,similar to signal 1212 of FIG. 12, to download the corresponding audiofile (block 1306).

The user device may be authenticated (block 1308). For example, deviceproxy 254 and/or VVM server 252 may authenticate mobile phone 220 using,for example, a session cookie sent in the audio file request (similar tosignal 1212). The audio file may be sent (block 1310). For example, VVMserver 252 may send a request (similar to signal 1214) to wireless VMserver 236 and may receive the audio file (similar to signal 1216). VVMserver 252 and may send the audio file (similar to signal 1218) tomobile phone 220 for playing to the user (block 1312). In oneembodiment, the audio file may be streamed from wireless VM server 236to mobile phone 220 for playing to the user (block 1312).

The message table in the user device may be updated (block 1314), e.g.,the state of the listened-to voicemail message may be changed. Forexample, the state of the voicemail message may be changed from NEW toHEARD or SAVE (e.g., in message table 464). A LISTEN message (e.g., astate change message) may be sent to a VM server (block 1316). Forexample, after playing the voicemail message, mobile phone 220 may senda LISTEN message (signal 1402) to VVM server 252. The LISTEN message(signal 1402) may include the device number (e.g., of mobile phone 220),the session cookie (for authentication), and the mailbox and message IDscorresponding to the listened-to message.

The LISTEN message may be received and forwarded (block 1318). Forexample, VVM server 252 may receive the message (signal 1402) and mayforward the message (signal 1404) to VM server 236. The LISTEN message(signal 1404) sent to wireless VM server 236 may include the devicenumber (e.g., of mobile phone 220), the message and mailbox IDs of thelistened-to message, and the PIN corresponding to the mailbox ID. VVMserver 252 and/or device proxy 254 may store the appropriate PIN, forexample, for the corresponding mailbox ID. In one embodiment, the userdevice sending the LISTEN message may be a different device than theuser device associated with the mailbox ID. For example, mobile phone220 (associated with wireless VM server 236) may send a LISTEN messageto home VM server 234 or work VM server 232, as well as wireless VMserver 236.

The VM server may update the message table (block 1320) corresponding tothe message ID. For example, wireless VM server 236 may update messagetable 600-3 to change the state of a message from NEW to HEARD.Likewise, VVM server 252 may also update its aggregate message table,such as message table 700, to change the state of the message from NEWto HEARD (e.g., VVM server 252 may change the status of the message inrecord 760 associated with mailbox MBC1 to HEARD). The LISTEN messagemay be acknowledged (block 1322). Wireless VM server 236 may send anacknowledgment message (signal 1406) to VVM server 252, which may bereceived and forwarded as an acknowledgment message (signal 1408) to theuser device, e.g., mobile phone 220.

A notification table may be queried (block 1324). For example, VVMserver 252 may query notification table 800 to determine which userdevices, if any, should be notified of the update to the aggregatemessage table that may have taken place at block 1320. One or morenotifications may be sent (block 1326). For example, if VVM server 252changed the status of a voicemail message associated with mailbox MBC1in response to a LISTEN message from mobile phone 220 (e.g., devicenumber 2022513434), then VVM server 252 may query notification table 800to determine that devices associated with device numbers 7035678989(e.g., smart phone 216) and 2023459292 (e.g., PDA 218) may be notifiedof the change in state. As shown in FIG. 14, a notification message(signal 1410) may be sent to smart phone 216 and a notification message(signal 1412) may be sent to PDA 218. Signals 1410 and 1412 may includethe same or similar information as the notification signal sent at block958 of process 900B. Alternatively, the notification signals (signals1410 and 1412) may include the mailbox ID, the message ID, and thecorresponding change (e.g., indicative of the state change from NEW toHEARD). Therefore, multiple user devices may be kept up-to-dateregarding information stored in the aggregate message table of VVMserver 252.

In another embodiment, a user device (e.g., mobile phone 220) may updatea VM server (e.g., wireless VM server 236) with state changes (e.g., aLISTEN message) at a different time, such as on a periodic basis or whenthe user terminates the VVM application in the user device. In oneembodiment, the user device may not change the state of a message in itsmemory until it receives an acknowledgment from the VM server.

After a user device downloads voicemail message information, the usermay perform various operations on a voicemail message, such as deletingor saving a voicemail message, that may change message tables in network200. FIG. 15 is a flowchart of an exemplary process 1500 for updating orchanging message tables in network 200. Process 1500 may begin after auser device receives a command to act on a voicemail message, forexample, and updates the message table stored in the device. Forexample, a user may enter a command into a user device to change thestate of a message from “SAVE” to “NEW.” In this case, the user devicemay update its message table to change the state of a message from“SAVE” to “NEW.” As another example, a user may enter a command into auser device to delete a message. In this case, the user device mayupdate its message table to change the state of a message from “HEARD”to “DELETE.” As yet another example, a user may enter a command into auser device to save a message. In this case, the user device may updateits message table to change the state of a message from “HEARD” to“SAVE.”

Process 1500 may be triggered by a change to any part of the messagetable stored in the user device (e.g., message table 464). If themessage table changes (block 1502: YES), then an UPDATE message, e.g., astate change message, may be sent (block 1504). If there is no change inthe message table (block 1502: NO), then process 1500 may wait untilthere is a change.

The UPDATE message may include a list of voicemail messages and thecorresponding change and may be sent to VVM server 252 or any one of VMservers 232-236. The UPDATE message may identify the messages to updateby their corresponding mailbox and message IDs. The UPDATE message mayalso include a session cookie to authenticate the user device, forexample. Examples of UPDATE messages include the LISTEN, DELETE, andSAVE messages described above.

The UPDATE message may be received and forwarded (block 1506). Forexample, VVM server 252 may receive the UPDATE message and may beforwarded to the appropriate VM server. The message table may be updated(block 1510). For example, the VM server that received the UPDATEmessage may update its message table. In addition, VVM server 252 mayalso update the aggregate message table.

A notification table may be queried (block 1512). For example, VVMserver 252 may query notification table 800, as described above withrespect to block 954 and process 900B. VVM server 252 may determinewhich devices may be notified based on the mailbox ID of the voicemailmessage information that has been updated. Notification messages may besent (block 1514). VVM server 252 may send a notification message, suchas signals 1008-1012, to user devices identified by the query in block1512. Such a notification message (sent at block 1514) may initiateprocess 1100 and the user devices may decide to synchronize as describedwith respect to process 1100. Therefore, a change to voicemail messageinformation in one device may be reflected across all devices that mayhave access to the same voicemail mailbox. In one embodiment, VM server252 may also, or alternatively, send a notification message, such assignal 902.

In one embodiment, methods and systems described above may allow for themanagement of email as well as voicemail.

U.S. patent application titled “MULTIPLE VISUAL VOICEMAIL MAILBOXES,”filed the same day herewith, is incorporated herein by reference.

In the preceding specification, various preferred embodiments have beendescribed with reference to the accompanying drawings. It will, however,be evident that various modifications and changes may be made thereto,and additional embodiments may be implemented, without departing fromthe broader scope of the invention as set forth in the claims thatfollow. The specification and drawings are accordingly to be regarded inan illustrative rather than restrictive sense.

While series of blocks have been described above with respect todifferent processes, the order of the blocks may differ in otherimplementations. Moreover, non-dependent acts may be performed inparallel.

It will be apparent that aspects of the embodiments, as described above,may be implemented in many different forms of software, firmware, andhardware in the embodiments illustrated in the figures. The actualsoftware code or specialized control hardware used to implement theseembodiments is not limiting of the invention. Thus, the operation andbehavior of the embodiments of the invention were described withoutreference to the specific software code—it being understood thatsoftware and control hardware may be designed to the embodiments basedon the description herein.

Further, certain portions of the invention may be implemented as “logic”that performs one or more functions. This logic may include hardware,such as an application specific integrated circuit, a field programmablegate array, a processor, or a microprocessor, or a combination ofhardware and software.

No element, act, or instruction used in the description of the presentapplication should be construed as critical or essential to theinvention unless explicitly described as such. Also, as used herein, thearticle “a” is intended to include one or more items. Where only oneitem is intended, the term “one” or similar language is used. Further,the phrase “based on” is intended to mean “based, at least in part, on”unless explicitly stated otherwise.

What is claimed is:
 1. A system comprising: one or more network devicesincluding: one or more memories including a first database to storevoicemail message information associated with a voicemail mailbox, and asecond database to associate a plurality of device numbers with thevoicemail mailbox, wherein each of a plurality of communication devicesis associated with a different one of the plurality of device numbers; areceiver to receive a new voicemail message associated with thevoicemail mailbox; a processor to query to the second database toretrieve the plurality of device numbers associated with the voicemailmailbox; and a transmitter to send a notification of the new voicemailmessage to each of the plurality of communication devices associatedwith the plurality of device numbers, wherein the notification indicatesa number of new voicemail messages associated with the voicemailmailbox, indicates a total number of voicemail messages associated withthe voicemail mailbox, and includes an identifier of the new voicemailmessage, wherein the notification causes each of the plurality ofcommunication devices to determine whether or not to request a list ofvoicemail messages associated with the voicemail mailbox based on thenumber of new voicemail messages from the notification, the total numberof voicemail messages from the notification, or the identifier of thenew voicemail message from the notification, wherein the notificationcauses one of the plurality of communication devices to determine torequest the list of voicemail messages based on the number of newvoicemail messages from the notification, the total number of voicemailmessages from the notification, or the identifier of the new voicemailmessage from the notification, and wherein the notification causes atleast another one of the plurality of communication devices to determinenot to request the list of voicemail messages based on the number of newvoicemail messages from the notification, the total number of voicemailmessages from the notification, or the identifier of the new voicemailmessage from the notification.
 2. The system of claim 1, wherein the oneof the plurality of communication devices includes a processor todetermine whether to request the list of voicemail messages based on thenumber of new voicemail messages, the total number of voicemailmessages, or the identifier of the new voicemail message.
 3. The systemof claim 2, wherein the processor of the one of the communicationdevices compares a list of voicemail message audio files stored in theone of the communication devices to the list of voicemail messages, anddetermines, based on the comparison, whether to request an audio filecorresponding to one of the voicemail messages in the list of voicemailmessages.
 4. The system of claim 3, wherein the one or more networkdevices further includes: a receiver to receive, from the one of thecommunication devices in response to the notification, a request for thelist of voicemail messages associated with the voicemail mailbox,wherein the list of voicemail messages includes a state of each of thevoicemail messages, wherein the transmitter sends, to the one of theplurality of communications devices, the list of voicemail messagesassociated with the voicemail mailbox, the list of voicemail messageslisting the new voicemail message.
 5. The system of claim 4, furthercomprising the one of the plurality of communication devices.
 6. Thesystem of claim 1, further comprising: a receiver to receive, from atleast three of the plurality of communication devices in response to thenotification, a request for the list of voicemail messages associatedwith the voicemail mailbox, wherein the receiver receives, from the oneof the plurality of communication devices, a state change messageassociated with one of the voicemail messages, wherein the processorupdates a state associated with the one of the voicemail messages in thefirst database based on the state change message.
 7. The system of claim6, wherein the state includes an indication of new, heard, saved, ordeleted.
 8. The system of claim 6, wherein the transmitter sends anothernotification to another one of the plurality of communication devices,the other notification indicative of the updated state.
 9. The system ofclaim 8, wherein the other notification includes an updated indicationof the number of new voicemail messages associated with the voicemailmailbox, an updated indication of the total number of voicemail messagesassociated with the voicemail mailbox, and an identifier of a mostrecent new voicemail message.
 10. A method comprising: storing a firstdatabase and a second database in one or more memories, wherein thefirst database includes voicemail message information associated with avoicemail mailbox in a memory, the second database to associate aplurality of device numbers with the voicemail mailbox, and each of aplurality of communication devices is associated with a different one ofthe plurality of device numbers; receiving a new voicemail messageassociated with the voicemail mailbox; querying the second database toretrieve the plurality of device numbers associated with the voicemailmailbox; and transmitting a notification of the new voicemail message toeach of the plurality of communication devices associated with theplurality of device numbers, wherein the notification indicates a numberof new voicemail messages associated with the voicemail mailbox,indicates a total number of voicemail messages associated with thevoicemail mailbox, and includes an identifier of the new voicemailmessage, wherein the notification causes each of the plurality ofcommunication devices to determine whether or not to request a list ofvoicemail messages associated with the voicemail mailbox based on thenumber of new voicemail messages from the notification, the total numberof voicemail messages from the notification, or the identifier of thenew voicemail message from the notification, wherein the notificationcauses one of the plurality of communication devices to determine torequest the list of voicemail messages based on the number of newvoicemail messages from the notification, the total number of voicemailmessages from the notification, or the identifier of the new voicemailmessage from the notification, and wherein the notification causes atleast another one of the plurality of communication devices to determinenot to request the list of voicemail messages based on the number of newvoicemail messages from the notification, the total number of voicemailmessages from the notification, or the identifier of the new voicemailmessage from the notification.
 11. The method of claim 10, furthercomprising determining, by the one of the plurality of communicationdevices, whether to request the list of voicemail messages based on thenumber of new voicemail messages, the total number of voicemailmessages, or the identifier of the new voicemail message.
 12. The methodof claim 11, further comprising: comparing, by the one of the pluralityof communication devices, a list of voicemail message audio files storedin the one of the communication devices to the list of voicemailmessages; and determining, by the one of the plurality of communicationdevices, based on the comparison, whether to request an audio filecorresponding to one of the voicemail messages in the list of voicemailmessages.
 13. The method of claim 11, further comprising: receiving,from the one of the communication devices in response to thenotification, a request for the list of voicemail messages associatedwith the voicemail mailbox; and transmitting, to the one of theplurality of communications devices, the list of voicemail messagesassociated with the voicemail mailbox, wherein the list of voicemailmessages lists the new voicemail message and includes a state of each ofthe voicemail messages.
 14. The method of claim 10, further comprising:receiving, from at least three of the plurality of communication devicesin response to the notification, a request for the list of voicemailmessages associated with the voicemail mailbox; receiving, from the oneof the plurality of communication devices, a state change messageassociated with one of the voicemail messages; and updating a stateassociated with the one of the voicemail messages in the first databasebased on the state change message.
 15. The method of claim 14, whereinthe state includes an indication of new, heard, saved, or deleted. 16.The method of claim 14, further comprising transmitting anothernotification to another one of the plurality of communication devices,the other notification indicative of the updated state.
 17. The methodof claim 16, wherein the other notification includes an updatedindication of the number of new voicemail messages associated with thevoicemail mailbox, an updated indication of the total number ofvoicemail messages associated with the voicemail mailbox, and anidentifier of a most recent new voicemail message.
 18. A systemcomprising: a communication device comprising: a receiver to receive anotification from a network device, the notification including anindication of a number of new voicemail messages in a voicemail mailbox,an indication of a total number of voicemail messages in the voicemailmailbox, and an identifier of a most recent new voicemail message in thevoicemail mailbox; a processor to: determine to request a list ofvoicemail messages based on the number of new voicemail messages, thetotal number of voicemail messages, or the identifier of the most recentnew voicemail message, wherein the list of voicemail messages includes astate of each of the voicemail messages, and determine not to requestthe list of voicemail messages based on the number of new voicemailmessages, the total number of voicemail messages, or the identifier ofthe most recent new voicemail message; and a transmitter to send arequest, when determined to request the list of voicemail messages, tothe network device for the list of voicemail messages in the mailbox,wherein the receiver receives the list of voicemail messages in themailbox from the network device; a memory to store voicemail messageaudio files and a corresponding list of voicemail message audio files,wherein the processor compares the list of voicemail message audio filesto the list of voicemail messages and determines, based on thecomparison, whether to request an audio file corresponding to one of thevoicemail messages in the list of voicemail messages, and wherein thetransmitter sends a request for the audio file to the network device.19. The system of claim 18, wherein the transmitter sends, to thenetwork device, a state change message associated with one of thevoicemail messages in the mailbox for updating a state associated withthe one of the voicemail messages in the mailbox based on the statechange message.
 20. The system of claim 18, further comprising thenetwork device, wherein the state or the state change includes anindication of new, heard, saved, or deleted.